This issue is caused by problem in the JBoss application server's run.sh script. The run.sh script contains a loop that waits for a value from the JBoss process stating that it is stopping. However, the JBoss process returns a value that the script does not expect, so the process continues to run.

To work around this problem, you must modify the loop so that it recognizes the value.

To update the script so that the loop recognizes the value that is returned, follow these steps:

1. Kill any running JBoss processes using the UNIX kill command.
2. Be sure to verify that all associated processes are also stopped using the following command:
   ps -ef | grep jboss
3. Search for the following lines in the run.sh file that is located in the JBOSS-directory-name\bin directory.
# Wait until the background process exits. WAIT_STATUS=0 while [ "$WAIT_STATUS" -ne 127 ]; do JBOSS_STATUS=$WAIT_STATUS wait $JBOSS_PID 2>/dev/null WAIT_STATUS=$? done fi
4. Replace those lines with the following lines:
   # Wait until the background process exits. WAIT_STATUS=128 while [ "$WAIT_STATUS" -ge 128 ]; do wait $JBOSS_PID 2>/dev/null WAIT_STATUS=$? if [ "${WAIT_STATUS}" -gt 128 ]; then SIGNAL='expr ${WAIT_STATUS} - 128' SIGNAL_NAME='kill -l ${SIGNAL}' echo "*** JBossAS process (${JBOSS_PID}) received ${SIGNAL_NAME} signal ***" >&2 fi done if [ "${WAIT_STATUS}" -lt 127 ]; then JBOSS_STATUS=$WAIT_STATUS else JBOSS_STATUS=0 fi fi
5. Submit the following command, which is located in the JBOSS-directory-name\bin directory to start the JBoss server:
   SASServer1.sh -start

Operating System and Release Information